System and method for generating patient test data processing code

ABSTRACT

A computer system for generating code for use in processing patient test data from point of care devices. The computer system comprises object definition storage storing a plurality of definition objects, each definition object defining a generic function to be performed in response to an output of a point of care device; instantiation data storage storing instantiation data for use in instantiating definition objects as processing objects for specific functions to be performed in response to outputs from specific point of care devices; and a code generating processor for generating code for at least one processing object to perform at least one specific processing function to process an output from a point of care device by accessing at least one definition object in the object definition storage and the instantiation data in the instantiation data storage to instantiate the at least one definition object using instantiation data for the point of care device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. application Ser. No. 15/521,455, filedApr. 24, 2017, which is national stage of PCT/GB2015/053099, filed Oct.19, 2015, which claims priority to U.K. Application No. 1419021.9, filedOct. 24, 2014, the entire disclosures of which are incorporated byreference herein.

FIELD OF THE INVENTION

The present invention generally relates to a system and method forgenerating code for processing patient test data from point of caredevices.

BACKGROUND OF THE INVENTION

Point-of-care testing (POCT) is medical testing at or near the site ofpatient care. The driving notion behind POCT is to bring the testconveniently and immediately to the patient. This increases thelikelihood that the patient, physician, and care team will receive theresults quicker, which allows for immediate clinical managementdecisions to be made. POCT includes: blood glucose testing, blood gasand electrolytes analysis, rapid coagulation testing, rapid cardiacmarkers diagnostics, drugs of abuse screening, urine strips testing,pregnancy testing, faecal occult blood analysis, food pathogensscreening, haemoglobin diagnostics, infectious disease testing andcholesterol screening.

POCT is often accomplished through the use of transportable, portable,and handheld instruments (e.g., blood glucose meter, nerve conductionstudy device) and test kits. Small bench analysers or fixed equipmentcan also be used when a handheld device is not available—the goal is tocollect the specimen and obtain the results in a very short period oftime at or near the location of the patient so that the treatment plancan be adjusted as necessary before the patient leaves. Cheaper,smaller, faster, and smarter POCT devices have increased the use of POCTapproaches by making it cost-effective for many diseases, such asdiabetes, carpal tunnel syndrome (CTS) and acute coronary syndrome.

There is a desire to get output of a POCT device made availableimmediately within an electronic medical record. The advantage of suchintegration into electronic medical health records is that results canbe shared instantaneously with all members of the medical team throughthe software interface enhancing communication by decreasing turnaroundtime (TAT). Also, errors caused by manual input are avoided. One of thechallenges accompanying the use of POCT is the plethora of devices andtests which brings with it a high degree of complexity in integratingthe POCT devices due to the lack of any agreed standard for data outputfrom such devices.

SUMMARY OF THE INVENTION

One aspect of the invention provides a computer system for generatingcode for use in processing patient test data from point of care devices,the computer system comprising object definition storage storing aplurality of definition objects, each definition object defining ageneric function to be performed in response to an output of a point ofcare device; instantiation data storage storing instantiation data foruse in instantiating definition objects as processing objects forspecific functions to be performed in response to outputs from specificpoint of care devices; and a code generating processor for generatingcode for at least one processing object to perform at least one specificprocessing function to process an output from a point of care device byaccessing at least one definition object in the object definitionstorage and the instantiation data in the instantiation data storage toinstantiate the at least one definition object using instantiation datafor the point of care device.

Another aspect of the invention provides a method of generating code foruse in processing patient test data from point of care devices, themethod comprising generating code for at least one processing object toperform at least one specific processing function to process an outputfrom a point of care device using at least one definition object andinstantiation data to instantiate the at least one definition objectusing instantiation data for a specific point of care device, eachdefinition object defining a generic function to be performed inresponse to an output of a point of care device, the instantiation datacomprising parameters for instantiating definition objects as processingobjects for specific functions to be performed in response to outputsfrom specific point of care devices; and storing the generated code.

Another aspect of the invention provides a computer system forgenerating code for use in processing patient test data from point ofcare devices, the computer system comprising object definition storagestoring a plurality of definition objects, each definition objectdefining a generic function to be performed in response to an output ofa point of care device; an interface for receiving instantiation datafor use in instantiating definition objects as processing objects forspecific functions to be performed in response to outputs from specificpoint of care devices; and a code generating processor for generatingcode for at least one processing object to perform at least one specificprocessing function to process an output from a point of care deviceusing at least one definition object in the object definition storageand the received instantiation data to instantiate the at least onedefinition object using instantiation data for the point of care device.

Another aspect of the invention provides a medium carrying data for usein generating code for processing patient test data from point of caredevices, the medium carrying data comprising a plurality of definitionobjects, each definition object defining a generic function to beperformed in response to an output of a point of care device; andinstantiation data for use in instantiating definition objects asprocessing objects for specific functions to be performed in response tooutputs from specific point of care devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a system for processing patient testdata according to one embodiment;

FIG. 2 is a schematic diagram of the details of the application serverof FIG. 1 according to one embodiment;

FIG. 3 is a schematic diagram of the details of the device interfacemodule of FIG. 2 according to one embodiment;

FIG. 4 is a schematic diagram of a point of care (POC) computeraccording to one embodiment;

FIG. 5 is a flow diagram illustrating the process on a server to developobject definitions and instantiation data for POC devices according toone embodiment;

FIG. 6 is a flow diagram illustrating the process on a server to developobject definitions and instantiation data for POC devices according toanother embodiment;

FIG. 7 is a flow diagram illustrating the process for processing patienttest data from a point of care device of a first type according to oneembodiment;

FIG. 8 is a flow diagram illustrating the process for processing patienttest data from a point of care device of a second type according to oneembodiment;

FIG. 9 is a flow diagram illustrating the process for processing patienttest data from a point of care device of a third type according to oneembodiment;

FIG. 10 is a diagram illustrating the data stored in a data medium forgenerating code for processing patient test data from point of caredevices according to one embodiment;

FIG. 11 is a schematic diagram of a development server for developingdefinition objects and instantiation parameters for generating code forprocessing patient test data according to one embodiment;

FIG. 12 is a schematic diagram of the details of an alternative deviceinterface module of FIG. 2 according to an alternative embodiment;

FIG. 13 is a schematic diagram of an alternative point of care (POC)computer according to an alternative embodiment;

FIG. 14 is a schematic diagram of the details of another alternativedevice interface module of FIG. 2 according to another embodiment; and

FIG. 15 is a schematic diagram of another alternative point of care(POC) computer according to another embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

A first generalised embodiment comprises a computer system forgenerating code for use in processing patient test data from point ofcare devices, the computer system comprising object definition storagestoring a plurality of definition objects, each definition objectdefining a generic function to be performed in response to an output ofa point of care device; instantiation data storage storing instantiationdata for use in instantiating definition objects as processing objectsfor specific functions to be performed in response to outputs fromspecific point of care devices; and a code generating processor forgenerating code for at least one processing object to perform at leastone specific processing function to process an output from a point ofcare device by accessing at least one definition object in the objectdefinition storage and the instantiation data in the instantiation datastorage to instantiate the at least one definition object usinginstantiation data for the point of care device.

As used herein, patient test data comprises any data output from pointof care devices, including test data for a patient test, calibrationdata from the calibration of the point of care device and any other dataoutput from the point of care device for regulatory or safety purposes.

In one embodiment, the instantiation data includes data identifying asequence of said definition objects for at least one said point of caredevice.

In one embodiment, the instantiation data includes parameters related tothe data expected to be output from the at least one point of caredevice and the data expected to be received by the at least one point ofcare device by the or each processing object in the course of the outputof a set of point of care data for a patient test.

In one embodiment, the computer system includes an interface forcommunication with a point of care device, and a user interface forreceiving instantiation parameters and definition object selections froma user; wherein the code generating processor is adapted to generatecode for at least one processing object according to the receivedinstantiation parameters and definition object selections, and to runthe generated code to attempt to process patient test data received fromthe point of care device; wherein the user interface is adapted todisplay result of the processing and to receive revised instantiationparameters and definition object selections from the user for generationand running of revised code by the code generating processor.

In one embodiment, the computer system includes a communicationinterface for transmitting the instantiation parameters to a point ofcare computer for storage at the point of care computer and for use atthe point of care computer in generating code for at least oneprocessing object to perform at least one specific processing functionto process an output from a point of care device by accessing at leastone stored definition object and the instantiation data to instantiatethe at least one definition object using instantiation data for thepoint of care device.

In one embodiment, the computer system includes a communicationinterface for transmitting the generated code for at least one point ofcare device to a point of care computer for the storage and running ofthe code to process patient test data received at the point of carecomputer from a point of care device.

In one embodiment, the computer system includes an interface to receivepatient test data from a point of care device, and a data processor forrunning the generated code to process the patient test data receivedfrom the point of care device.

A second generalised embodiment provides a method of generating code foruse in processing patient test data from point of care devices, themethod comprising generating code for at least one processing object toperform at least one specific processing function to process an outputfrom a point of care device using at least one definition object andinstantiation data to instantiate the at least one definition objectusing instantiation data for a specific point of care device, eachdefinition object defining a generic function to be performed inresponse to an output of a point of care device, the instantiation datacomprising parameters for instantiating definition objects as processingobjects for specific functions to be performed in response to outputsfrom specific point of care devices; and storing the generated code.

In one embodiment, the instantiation data includes data identifying asequence of said definition objects for at least one said point of caredevice.

In one embodiment, the instantiation data includes parameters related tothe data expected to be output from the at least one point of caredevice and the data expected to be received by the at least one point ofcare device by the or each processing object in the course of the outputof a set of point of care data for a patient test.

In one embodiment, the method includes receiving instantiationparameters and definition object selections from a user interface;generating the code for at least one processing object according to thereceived instantiation parameters and definition object selections,attempting to run the code to process patient test data received fromthe point of care device; displaying a result of the processing;receiving revised instantiation parameters and definition objectselections from the user interface; and generating and running revisedcode for at least one processing object according to the revisedinstantiation parameters and definition objects.

In one embodiment, the method includes transmitting the instantiationparameters to a point of care computer for storage at the point of carecomputer and for use at the point of care computer in generating codefor at least one processing object to perform at least one specificprocessing function to process an output from a point of care device byaccessing at least one stored definition object and the instantiationdata to instantiate the at least one definition object usinginstantiation data for the point of care device.

In one embodiment, the method includes transmitting the generated codefor at least one point of care device to a point of care computer forthe storage and running of the code to process patient test datareceived at the point of care computer from a point of care device.

In one embodiment, the method includes receiving patient test data froma point of care device, and a data processor for running the generatedcode to process the patient test data received from the point of caredevice.

A third generalised embodiment provides a computer system for generatingcode for use in processing patient test data from point of care devices,the computer system comprising object definition storage storing aplurality of definition objects, each definition object defining ageneric function to be performed in response to an output of a point ofcare device; an interface for receiving instantiation data for use ininstantiating definition objects as processing objects for specificfunctions to be performed in response to outputs from specific point ofcare devices; and a code generating processor for generating code for atleast one processing object to perform at least one specific processingfunction to process an output from a point of care device using at leastone definition object in the object definition storage and the receivedinstantiation data to instantiate the at least one definition objectusing instantiation data for the point of care device.

In one embodiment, the instantiation data includes data identifying asequence of said definition objects for at least one said point of caredevice.

In one embodiment, the instantiation data includes parameters related tothe data expected to be output from the at least one point of caredevice and the data expected to be received by the at least one point ofcare device by the or each processing object in the course of the outputof a set of point of care data for a patient test.

A fourth generalised embodiment provides a medium carrying data for usein generating code for processing patient test data from point of caredevices, the medium carrying data comprising a plurality of definitionobjects, each definition object defining a generic function to beperformed in response to an output of a point of care device; andinstantiation data for use in instantiating definition objects asprocessing objects for specific functions to be performed in response tooutputs from specific point of care devices.

In one embodiment a non-transient storage medium stores computerreadable code for controlling a computer to carry out any of the methodsas described above.

In one embodiment a carrier medium carries computer readable code forcontrolling a computer to carry out any of the methods as describedabove.

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof, and in which is shown byway of illustration specific embodiments in which the inventive subjectmatter may be practiced. These embodiments are described in sufficientdetail to enable those skilled in the art to practice them, and it is tobe understood that other embodiments may be utilized and thatstructural, logical, and electrical changes may be made withoutdeparting from the scope of the inventive subject matter. Suchembodiments of the inventive subject matter may be referred to,individually and/or collectively, herein by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed.

The following description is, therefore, not to be taken in a limitedsense, and the scope of the inventive subject matter is defined by theappended claims.

The functions or algorithms described herein are implemented inhardware, software or a combination of software and hardware in oneembodiment. The software comprises computer executable instructionsstored on computer readable media such as memory or other type ofstorage devices, or any other form of media such as a signal. Further,described functions may correspond to modules, which may be software,hardware, firmware, or any combination thereof. Multiple functions areperformed in one or more modules as desired, and the embodimentsdescribed are merely examples. The software is executed on a digitalsignal processor, ASIC, microprocessor, or other type of processoroperating on a system, such as a personal computer, server, a mobiledevice, or other device capable of processing data including networkinterconnection devices. The network can comprise a wired or wirelessnetwork and includes a private network, a virtual private network (VPN),a Local Area Network (LAN), a Wide Area Network (WAN) and the internetfor example. Although in the following detailed embodiment theinterconnection between computers is shown over the internet, theinvention encompasses any form of network connection.

Some embodiments implement the functions in two or more specificinterconnected hardware or software modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexemplary process flow is applicable to software, firmware, and hardwareimplementations.

Embodiments of the present invention can be implemented on any form ofcomputing hardware using one or more computer programs or applications(software). The computer program(s) can be provided to a computer on anysuitable carrier medium. One such type of medium is a computer storagemedium which represents a non-transient medium. Computer storage mediainclude random access memory (RAM), read only memory (ROM), erasableprogrammable read-only memory (EPROM) and electrically erasableprogrammable read-only memory (EEPROM), flash memory or other memorytechnologies, compact disc read-only memory (CD ROM), Digital VersatileDisks (DVD) or other optical disk storage, magnetic cassettes, magnetictape, magnetic disk storage or other magnetic storage devices, or anyother medium capable of storing computer-readable instructions. Anotherform of medium is a transient medium such as a signal. A signal cancomprise an electrical signal over a wire, an electromagnetic signaltransmitted over a wire or wirelessly, an optical signal, an acousticsignal, or even a magnetic signal. Once common form of signal istransmitted over a communication network, which can be wired or wirelessor a combination of both, e.g. a local area network (LAN), a wide areanetwork (WAN) or the internet.

The point of care devices can comprises any device for carrying out anypatient medical test at a point of care facility or even at the patientspremises, such as blood glucose testing, blood gas and electrolytesanalysis, rapid coagulation testing, rapid cardiac markers diagnostics,drugs of abuse screening, urine strips testing, pregnancy testing,faecal occult blood analysis, food pathogens screening, haemoglobindiagnostics, infectious disease testing and cholesterol screening. Themedical test data can also include patient vitals such as blood pressureand heart rate and patient data such as height, weight, age etc. A pointof care facility can comprise any medical facility capable of providingsuch patient tests and test data such as a doctor's surgery, a clinic,or a specialist centre. Where a point of care device is used by apatient in their own facilities either by themselves or by a visitingmedical practitioner, the patient test data can be obtained as an outputfrom the device on a storage media for later upload to a point of carecomputer, or as a signal to be transmitted over a communications network(wired or wireless) to the point of care computer. A point of carecomputer is generally a computer provides at the point of care facilityfor direct connection to the point of care devices. However, the pointof care computer can be any computer connected by a suitablecommunication connection to the point of care device or devices for thereception of patient test data from the point of care device. Such acommunication connection can be via intermediary networks and computerswhich perform no processing of the patient test data. The processing ofthe patient test data and two way communication with point of caredevice is achieved using the program code in the point of care computer.The point of care computer can hence comprise a client in a computernetwork or a server.

There are no standards covering the format of the data output frompoints of care devices. Each device can output data in a proprietaryformat dependent upon a manufacturer and/or a type of point of caredevice (i.e. the type of patient test). Point of care devices providedata outputs which can require two way communication between a point ofcare computer connected to the point of care device during the dataoutput and can provide a communication in the form of a communicationpattern or sequence of data packages or communication messages. Theindividual packages, messages or parts can themselves conform to apattern or structure which can be classified or defined generically fora number of specific data packages, messages or parts of an output for anumber of point of care devices.

A generalised embodiment provides a library of definition objects whichhave been developed by system developers to define a generalisedfunction or function relating to processing an output of a point of caredevice. The processing can comprise a simple handshake e.g. respondingto an enquiry with an acknowledgement or more complex processing whichcan include the storage of a package of data (the message payload). Theprecise form of the message protocol for point of care devices is notincluded in the definition objects. The details of this are separatelydefined for each point of care device in the form of objectinstantiation parameters. In this way the combination of a genericdefinition object with instantiation parameters, provides the necessarylogic for processing a part (or the whole) of a communication from apoint of care device. The instantiation parameters can also includeinformation identifying a sequence of definition objects required forthe instantiation of a complete communication output from a point ofcare device. Thus the library of definition objects can include the coderequired for the generation of building of code for a plurality of pointof care devices simply by instantiation the definition objects. Hencethe definition objects act as the building blocks for the formation ofcode for the processing of communications with point of care devices.This reduces the requirement for new code to be developed every time anew point of care device is required to be interfaced to a point of carecomputer to upload the patient test data there from. Also, the storageof parameters with a generalised set of definition objects reducesprovides for efficient storage. It is not necessary to store a completeset of code for each point of care device. Code from the library can bereused as generalised definition objects. Code for each point of caredevice can be efficiently generated or built using the code objectblocks.

In one embodiment, to avoid the need to transmit code from a server suchas a centralised service or development server, the point of carecomputer can be provided with the library of definition objects and onlythe instantiation parameters need be transmitted over the network forinstantiating the definition objects to generate code to configure thepoint of care computer to process data from point of care devices.

Embodiments of the invention can be implemented with the systems andmethods disclosed in U.S. Pat. No. 10,930,376, and co-pendingapplication number GB 25332910 A, filed herewith by the same applicantsand entitled “Wireless processing unit and method for collecting patienttest data from point of care devices”, the contents of both of which arehereby incorporated in their entirety by reference.

A first embodiment of the present invention will now be described withreference to FIG. 1.

FIG. 1 schematically illustrates a patient test data gathering andprocessing system. Point of care devices 11 a to 11 d are provided toobtain patient test data. The point of care devices 11 a to 11 f areconnected to interfaces in respective point of care (POC) computers 20and 30. The POC computers 20 and 30 are provided at POC facilities oraccessible to POC facilities. The POC devices 11 a to 11 f may bepresent at the POC facility or used at a remote location when portablee.g. at the patients premises or in a mobile facility. The POC devices11 a to 11 f generate output patient test data as a result of a testbeing performed by an operator on a patient. The patient test data canbe output using any known convenient method which depends upon theoutput capabilities of the POC device and includes:

From POC device A (11 a) over a serial computer line to a serialcomputer port in the POC computer 30From POC device B (11 b) over a USB link to a USB computer port in thePOC computer 30From POC device C (11 c) over a wireless Wi-Fi link to a wireless portin the POC computer 20From POC device D (11 d) over a Bluetooth® link to a Bluetooth® port inthe POC computer 20From POC device E (11 e) over an Ethernet line to an Ethernet port inthe POC computer 20From POC device F (11 f) over an internet connection to a an internetnetwork interface the POC computer 20From a POC device the patient test data can also be stored onto astorage device such as a solid state memory device, an optical disk oreven a magnetic disk to be read by an appropriate storage device in thePOC computer.

The POC computer 20 and 30 comprises any suitable computing device suchas a general purpose computer, a mobile device, a laptop, tabletcomputer etc. The POC computer 20 and 30 has a connection via a networkinterface to the internet 10 over a wired or wireless network to provideaccess to send and receive data over a network such as the internet 10.

Electronic health records (EHR) are stored and maintained by EHRproviders. There are a number of such providers available and differentmedical care providers use different EHR providers. The EHR providershost the EHR records in databases 43 and 53 on computers 40 and 50. EachEHR provider's computer 40 and 50 implements a web server 42 and 52 forinterfacing via a network interface to the internet 10 and anapplication server 41 and 51 for providing the required functionalityand interface to the respective EHR databases 43 and 53.

In this embodiment, the patient test data processing is hosted in aservice provider's computer 60 comprising a server system implementing aSoftware as a Service model, where a ‘thin client’ in the form of aclient application is implemented on each POC computer 20 and 30. On theservice provider's computer 60 web services are implemented to providethe functionality. On the POC computer 30 and 30 a Windows® service isimplemented to provide the functionality.

As shown in FIG. 1 schematically, a web server 61 is provided withaccess to web server data 66 to provide a web interface to the POCcomputers 20 and 30. This enables an operator to login into the serviceand interact with interfaces generated by the web server 61 e.g. to viewlists of and select cached patient test data, to input any requiredadditional patient test data, to access and input operator qualificationdata etc. An application server 62 is provided to provide thefunctionality and access the device and user database 63, the test datadatabase 64 and the compliance database in the data warehouse 600. Boththe application server 62 and the web server 61 are connected by anetwork interface 67 to the internet 10.

In the embodiment illustrated in FIG. 1, the system operates such thatthe operators of the POC devices 11 a to 11 f and the POC computers 20and 30 require access to the EHR records hosted by the EHR provider'scomputers 40 and 50 i.e. the POC facility does not have its ownproprietary EHR and instead access EHR providers available to many POCfacilities and providers.

FIG. 2 is a schematic diagram of the application server 62 of theembodiment of FIG. 1, hosted on the service provider's computer system60 according to one embodiment. The application server 62 operates acore web services module 610 which has access to a cache memory 670 fortemporary storage of patient test data pending approval and completionby operators, and which provides an interface 640 to a data warehouse600. A compliance module 650 is implemented to provide regulatorycompliance functionality. A reports module 660 is provided to enableusers of the service with access to reports on patient tests andcompliance. A device interface module 620 is provided which implementsspecific device modules 621 dependent upon the identity of the devicesdetected in the patient test data. The device modules 621 receive thepatient test data and perform device specific processing on it, namelythe data which is in a format specific to the device is parsed using aparser specific to the device to reformat the data according to a testtype object dependent upon the test type identified for the patient testdata. The patient test data reformatted according to the identified testtype can then be stored in the cache 670 pending approval and completionby the operator. An EHR interface 630 is also provided and implementsEHR modules 631 which are specific to the EHR provider to which thepatient test data is to be transmitted. The EHR provider can beidentified from an order identifier associated with the patient test.When a medical practitioner places an order for a POCT in an EHR, theorder is assigned a unique identifier and it is associated with thepatient record and patient identifier in the EHR. When a patient test isperformed an operator will input a patient name or identifier enablingthe order to be found in the EHR and hence associated with the patienttest data in the cache 670 of the service provider's computer 60 pendingcompletion and acceptance of the patient test data by the operator. Inan alternative embodiment, for some patient test data, such a patientvitals (e.g. heart rate, blood pressure), there may be no order in theEHR system. In this embodiment, a patient record in the EHR can beidentified from a patient ID or name and the test data can be pushed upto the EHR provider's computer 40 and 50 for storage of the test data inthe EHR record for the patient in the EHR database.

The device modules 621 comprise code capable of recognising the messagesfrom the POC devices. Parsing is performed by the device modules 621 bytaking the patient test data from the POC device and formatting thepatient test data according to a test type determined from a test typelibrary on the basis of the POC device name. In other words, each devicemodule 621 is associated with a test type since it is associated with adevice type, which can only produce patient test data of a certain testtype. More than one device type can be associated with a test type,since different device types could be used to provide a test of the sametype e.g. ABC Inc's Blood Monitor is one device type and XYZ's BloodMonitor is another device type but both provide patient test data of thesame test type—Blood Test A.

FIG. 3 is a schematic diagram of the device interface 620 of FIG. 2 inmore detail. A processor 624 is provided to access an object definitionlibrary 623 and an instantiation parameter data store 622. Acommunications port 680 is provided in the service provider's computer60 to provide communications with a point of care device 11. Theprocessor 624 executes code to execute the device modules 621. The codecan be stored in the object definition library 623 as generalisedobjects with instantiation parameters stored in the parameter data store622. In this way, the required code for processing data of a test typecan be generated by instantiating objects dependent upon the test type.The processor 624 can look up appropriate instantiation parameters forone or more objects based on the test type, which can be indicated in orbased on a parameter sent from the point of care device. Theinstantiation parameters can include parameters identifying the objectsand any order of implementation of the objects for the orderedprocessing of the patient test data.

The processor 624 is also operable to enable a user to access the objectdefinition library 623 via the core web services module 610 using a webbrowser to be able to select of add objects and to access theinstantiation parameter data store 622 to select and change or addinstantiation parameters in a development process which will bedescribed in more detail herein after with reference to FIGS. 5 and 6.

FIG. 4 is a schematic diagram of a point of care computer 30 accordingto one embodiment. The POC computer is illustrated as just connected toone POC device. Of course, as shown in FIG. 1, it can be connected tomany.

A processor 101 of the POC computer 30 executes code to implement a dataprocessor 103 for receiving and sending communications from and to thePOC device 11 via a communications port 104. The data processor 103performs the process of communications control to control the receptionand transmission of communications to the POC device 11 and thetransmission and reception of communications over a network interface107 to the service provider's computer 60.

A definition object library 102 is provided storing the definitionobjects which can be used to generate or build the code for controllingcommunications with a POC device 11 i.e. processing patient test dataoutput from the POC device 11. An instantiation data store 111 is alsoprovided for storing instantiation parameters for definition objects forthe generation or building of processing code for specific POC devices.The processor 1010 executes code to implement an instantiation enginefor the generation of code by the instantiation of definition objects.The generated code is stored in the generated code store 105 for readingand execution by the data processor 103. The processor 101 can alsoexecute code to implement a web browser 108 to provide a user with aninterface to the functions of the service provider's computer. In suchan embodiment, the POC computer is provided with a user interface 109 toenable the input and output of information e.g. a display, keyboard, apointing device, a touch sensitive display etc. However, it is notrequired for the POC computer to have any user interface 109 (and henceno web browser 108). The POC computer can simply be connected over anetwork to the service provider's computer 60. The provision of theinstantiation parameters can be by download from the service provider'scomputer 60.

Hence, in the embodiment of FIG. 4, the POC computer is provided withthe definition object library 102 to enable it to build or generate anyPOC device processing code for controlling communications with the POCdevice to capture the output data and pass it onto the serviceprovider's computer 60. Instantiation data is all that is required toenable the building or generation of the required code to process theoutput of a required POC device.

FIG. 5 is a flow diagram illustrating the process to develop definitionobject and instantiation parameters for POC devices according to oneembodiment. The process can be implemented on the service provider'scomputer 60 or a separate development server 70 as will be describedherein after with reference to FIG. 11. The process is hence run by adeveloper of POC device specific interface code.

In step S1 a user selects to add new interface code specific to a newPOC device. The user can select in step S2 whether to select one or aset of definition objects currently available in the definition objectlibrary 623 (step S3) or to input information to build a new object fora POC device (step S4). The building of a new definition object cancomprise entering code or using a code building interface. In step S5user input instantiation parameters are received and the process loopsat step S6 until all the required definition objects and instantiationparameters have been input or selected.

In step S7 the definition objects are instantiated and executed and instep S8 the POC device 11 is connected to the communication port 680 anda patient test data transmission output is initiated. The communicationsfrom the POC device are received at the POC computer in step S9 and thedeveloper checks to determine whether the resulting data is what isexpected from the POC device (step S10). If not, the process returns tostep S2 to repeat the process until the expected results are achievedand hence the correct definition objects and instantiation parametershave been developed. These are then stored in step S12.

FIG. 6 illustrates an alternative development process to that of FIG. 5,in which the developed code is tested on the fly, object by object(function by function).

In step S20 a user selects to add new interface code specific to a newPOC device. The communications from the POC device are received at thePOC computer in step S21. The user can select in step S22 whether toselect one or a set of definition objects currently available in thedefinition object library 623 (step S23) or to input information tobuild a new object for a POC device (step S24). The building of a newdefinition object can comprise entering code or using a code buildinginterface. In step S25 user input instantiation parameters are received.In step S26 the definition object(s) are instantiated and executed andif the part of a message is processed, the process loops at step S27until all the required definition objects and instantiation parametershave been input or selected for a message part. In step S28 thedefinition object(s) and the instantiation data is stored for themessage part. In step S29 it is then determined whether the message fromthe POC device is complete (i.e. all message parts processed) and if notthe process loops back to step S22 until all are completed. Thedefinition objects and instantiation parameters are then stored in stepS30.

The process of FIG. 5 or 6 enable developers to develop POC device codeto be downloaded to POC computers either in the form of instantiationparameters or even as full sets of code build using the instantiationparameters and the definition objects at the server, as will bedescribed in more detail herein after.

Examples of POC device code implementation and the related instantiationdata and definition objects will now be described with reference toFIGS. 7 to 10.

FIG. 7 illustrates a process implemented by processing code forprocessing data from a POC device of type A. In this embodiment, the POCdevice communicates using the ASTM communication protocol. A typicalcommunication session to output a message comprises a plurality ofmessage parts as shown in table I below. The communication between thePOC device and the POC computer is two way. The POC computer musttransmit an <ACK> character at the end of receipt of each message partto prompt the POC device to send the next.

TABLE 1 the ASTM communication protocol Receiver Sender (PCC) Direction(LIS) Description <ENQ> --> Notifying receiver that there is informationto send. <-- <ACK> LIS sends back an ACK, if it is ready. <STX>1HMessage<ETX><CS><CR><LF> --> Header record <-- <ACK> <STX>2PMessage<ETX><CS><CR><LF> --> Patient record <-- <ACK> <STX>3OMessage<ETX><CS><CR><LF> --> Order record <-- <ACK> <STX>4RMessage<ETX><CS><CR><LF> --> First result record <-- <ACK> <STX>5RMessage<ETX><CS><CR><LF> --> Second result record <-- <ACK> . . .<STX>?L Message<ETX><CS><CR><LF> --> Terminator record <-- <ACK> <EOT>--> Message complete transmitted.

Using this protocol, a partial message can be transmitted with aterminating character <ETB> rather than <ETX> to indicate that thefollowing message part should be concatenated with the current messagepart.

The communication characters comprise:

<ENQ>—ASCII 0x05 <STX>—ASCII 0x02 <ETX>—ASCII 0x03 <EOT>—ASCII 0x04<ACK>—ASCII 0x06 <ETB>—ASCII 0x17

In step S40 of FIG. 7 the POC computer waits in a monitoring state toreceive a message on an Ethernet port in this embodiment. The functionof monitoring a port can be coded as a definition object, e.g. objecttype A. In this instance the object is instantiated by instantiationdata to monitor the Ethernet port and hence it is an object type Ainstantiation 1. In step S41 the process determines whether thecommunication is <ENQ> and if so, a temporary storage buffer for messageparts is cleared in step S42 and in step S43 the POC computer returns<ACK> and waits for the next message (step S40). This part of theprocessing by the POC computer comprises the function of identifying theinitiating of a message part, clearing the buffer ready to receive themessage part and sending an acknowledgement. This function can be codedas a definition object of type B. It is instantiated with parameterssuch as the initiating character <ENQ> and response character of <ACK>and hence it is an object type B instantiation 1.

If the communication is not <ENQ> and is instead a message part framedby <STX> and <ETB> (step S44) or <STX> and <ETX> (step S47), in step S45the POC computer writes the message part to the buffer and in step S46returns <ACK> and waits for the next message (step S40). This part ofthe processing by the POC computer comprises the function of identifyinga frame of a message block, storing it and sending an acknowledgement.This function can be coded as a definition object of type C. It isinstantiated with parameters such as the message frame characters <STX>and <ETB> or <STX> and <ETX> and response character of <ACK> and henceit is an object type C instantiation 1. In this embodiment theprocessing of the message frame part <STX><ETB> and <STX><ETX> aredefined by the same definition object since the only different is in theinstantiation with the frame end character <ETB> and <ETX>. In analternative embodiment, since the storing of the partial frameterminated with <ETB> requires the concatenation with the next frame, aseparate definition object can be defined for this different processingfunction.

If the communication is <EOT> (step S48), the completed message storedin the buffer is transmitted by the POC computer 30 over the network 10to the service provider's computer 60 (step S49) and an ACK response isreturned to the POC device. The POC computer 30 then waits for the nextmessage (step S40). This function can be coded as a definition object oftype D. It is instantiated with parameters such as the character <EOT>and details of the service to which the message is transmitted and thecharacter <ACK> and hence it is an object type D instantiation 1.

If the POC computer detects a message character other than <ENQ>, <STX>or <EOT>, an error message is generated in step S50.

Hence, in this embodiment, the code required by the POC computer 30 toprocess communications with a POC device 11 is based on theinstantiation of four definition objects.

FIG. 8 illustrates a process implemented by processing code forprocessing data from a POC device of type B. In this embodiment, likethe previous embodiment the POC device communicates using the ASTMcommunication protocol. As before, the communication between the POCdevice and the POC computer is two-way. The POC computer must transmitan <ACK> character at the end of receipt of each message part to promptthe POC device to send the next.

In step S60 the POC computer waits in a monitoring state to receive amessage on a USB port in this embodiment. The function of monitoring aport can be coded as a definition object, e.g. object type A. In thisinstance the object is instantiated by instantiation data to monitor theUSB port and hence it is an object type A instantiation 2. In step S61the process determines whether the communication is <ENQ> and if so, atemporary storage buffer for message parts is cleared in step S62 and instep S63 the POC computer returns <ACK> and waits for the next message(step S60). This part of the processing by the POC computer comprisesthe function of identifying the initiating of a message part, clearingthe buffer ready to receive the message part and sending anacknowledgement. This function can be coded as a definition object oftype B. It is instantiated with parameters such as the initiatingcharacter <ENQ> and response character of <ACK> and hence it is anobject type B instantiation 1.

If the communication is not <ENQ> and is instead a message part framedby <STX> and <ETX> (step S64), in step S65 the POC computer writes themessage part to the buffer and in step S66 returns <ACK> and waits forthe next message (step S60). This part of the processing by the POCcomputer comprises the function of identifying a frame of a messageblock, storing it and sending an acknowledgement. This function can becoded as a definition object of type C. It is instantiated withparameters such as the message frame characters <STX> and <ETX> andresponse character of <ACK> and hence it is an object type Cinstantiation 2.

If the communication is <EOT> (step S67), the completed message storedin the buffer is transmitted by the POC computer 30 over the network 10to the service provider's computer 60 (step S68) and an ACK response isreturned to the POC device. The POC computer 30 then waits for the nextmessage (step S60). This function can be coded as a definition object oftype D. It is instantiated with parameters such as the character <EOT>and details of the service to which the message is transmitted and thecharacter <ACK> and hence it is an object type D instantiation 1.

If the POC computer detects a message character other than <ENQ>, <STX>or <EOT>, an error message is generated in step S69.

Hence, in this embodiment, the code required by the POC computer 30 toprocess communications with a POC device 11 is based on theinstantiation of the same four definition objects as the embodiment ofFIG. 7. However, this embodiment differs in that the processing of thecommunications with the type B POC device is characterised by adifferent instantiation of object C: there are no partial message framesframed by <STX> and <ETB> in this embodiment.

FIG. 9 illustrates a process implemented by processing code forprocessing data from a POC device of type C. In this embodiment, the POCdevice communicates using a different communication protocol. As before,the communication between the POC device and the POC computer is twoway. In this embodiment, there is no transmission of an <ACK> characterat the end of receipt of each message part to prompt the POC device tosend the next.

In step S80 the POC computer waits in a monitoring state to receive amessage on a serial port in this embodiment. The function of monitoringa port can be coded as a definition object, e.g. object type A. In thisinstance the object is instantiated by instantiation data to monitor theserial port and hence it is an object type A instantiation 3. In stepS81 the process determines whether the communication is <VT> and if so,the data is received from the POC device 11 and stored in a temporarybuffer (step S82) until <CR><FS<CR> is received from the POC deviceindicating the end of the message (step S83). This function can be codedas a definition object of type E. It is instantiated with parameterssuch as the character <VT> and the character sequence <CR><FS<CR>.

When receipt of the message is complete the data is read from the bufferand transmitted by the POC computer 30 over the network 10 to theservice provider's computer 60 (step S84) and an <ACK> is returned tothe POC device. The POC computer 30 then waits for the next message(step S80). This function can be coded as a definition object of type F.It is instantiated with parameters such as the details of the service towhich the message is transmitted and the character <ACK> and hence it isan object type F instantiation 1.

If the POC computer detects a message character other than <VT>, anerror message is generated in step S85.

FIG. 10 is a diagram illustrating the definition objects and theinstantiation data stored for the three embodiments described withreference to FIGS. 7 to 9.

For each POC device type, in the service provider's computer 60 inaddition to the library of definition objects, instantiation data isstored. The instantiation data comprises instantiation data for eachdefinition object and can include parameters identifying the sequence ofobjects in the processing of the communications with the POC device. Inone embodiment, the type A and B POC devices may transmit a known numberof message parts processed by definition objects C and hence thesequence is defined by instantiation parameters. In another embodiment,the number of message parts transmitted by a POC device might varydepending upon the nature of the patient test data e.g. whether a testwas run for 1 hour or 2. In such an embodiment, the instantiationparameters for object type C for POC devices type A and B can simplyinstantiate a conditional clause in the function requiring the code toidentify if the message is <STX> or <EOT> and invoke the instantiateddefinition object accordingly.

Although the previous embodiments have been described with reference tothe ASTM protocol, embodiments are applicable to any communicationprotocol used by POC devices.

FIG. 11 is a schematic diagram of a development server 70 for use withthe system of FIG. 1 in accordance with one embodiment of the invention.

The development server 70 includes a network 725 for connection to anetwork such as the internet for communication with the serviceprovider's computer 60. The development server 70 includes a deviceinterface module 720 which performs similar functions to the deviceinterface module of FIG. 3. A model processor 721 is provided to accessan object definition library 723 and an instantiation parameter datastore 722. A communications port 724 is provided to providecommunications with a point of care device 11. The processor 721 isoperable to enable a user to access the object definition library 723 auser interface 726 to be able to select of add objects and to access theinstantiation parameter data store 722 to select and change or addinstantiation parameters in a development process which is described inmore detail with reference to FIGS. 5 and 6.

This embodiment enables a developer to develop the definition objectsand instantiation parameters in a development environment away from theservice provider's computer 60. The developed definition objects andinstantiation parameters can then be uploaded to the service provider'scomputer 60 from the development server 70 for storage in the definitionobject library 623 and instantiation parameter data store 622. Anyrevisions to the definition object library 623 can be transmitted to allPOC computers 20 and 30 connected over the network to the serviceprovider's computer 60 for storage in the definition object library 102so that each POC computer has available all of the object for all knowPOC devices. The instantiation parameters will be downloaded by the POCcomputers when needed for the instantiation of the definition objects togenerate the code for communication with the POC device.

FIG. 12 is a schematic diagram of the device interface 620 of FIG. 2according to another embodiment. This embodiment has similar featuresand functionality to those of the embodiment of FIG. 3. This embodimentdiffers in that a POC device data processing code store 625 is providedin which is stored code for execution by the POC computers tocommunicate with the POC devices. The model processor 624 generates thecode using the instantiation parameters for definition objects for POCdevices to provide a library of code which can be downloaded to the POCcomputers for execution when required for new POC devices connected tothe POC computers. Hence, this embodiment differs from the embodiment ofFIG. 3 in that instead of downloading just instantiation parameters tothe POC computers, POC device data processing code is downloaded readyfor execution by the POC computer.

FIG. 13 schematically illustrates a POC computer 30 for use with thedevice interface module 620 of the embodiment of FIG. 12. Thisembodiment is similar to the embodiment of FIG. 4 except that there isno instantiation data store, instantiation engine, definition objectlibrary or generated code store. Instead, the data processor 103 simplyaccesses a POC device data processing code store 130 to access andexecute the required code for communication with the POC device.

FIG. 14 schematically illustrates a device interface module 620according to another embodiment. This embodiment is similar to theembodiment of FIG. 12 except that there is additionally provided a dataprocessor 625 for executing the POC device data processing code in thecode store 624.

FIG. 15 is a schematic diagram of a POC computer for use with theembodiment of FIG. 14. This embodiment differs from the embodiment ofFIG. 13 in that the processor does not implement a data processor usingcode in a POC device data processing code store. Instead a datacommunicator 110 is implemented by the processor 101 to simply act topass on communications received from the POC device to the serviceprovider's computer 60. The processing of the communications isperformed in the device interface module 620 by the data processor 625.Hence, in this embodiment, the POC computer 30 acts as a ‘thin client’and acts as nothing more than a router of communications to the serverfor processing. In this embodiment the server is providing the POCcomputer function. This avoids the need for the transmission and copyingof code or instantiation parameters to the POC computer. However, thenetwork needs to be fast to avoid transmission delays which can causethe POC device to time out during a communication if the handshaking isnot quick enough.

In the embodiments described, the system and method is able to managethe development of new POC device processing code by developing,maintaining and utilising a library of definition objects which can beused for processing a plurality of POC device communications. Eachdefinition object comprising generic code for defining or performing afunction, which can comprise part of a complete communication with a POCdevice. Instantiation parameters can be developed and stored separatelyto instantiate the definition objects for use in the generation of POCdevice data processing code. This provides a more flexible codedevelopment and deployment system.

It will be readily understood to those skilled in the art that variousother changes in the details, material, and arrangements of the partsand method stages which have been described and illustrated in order toexplain the nature of the inventive subject matter may be made withoutdeparting from the principles and scope of the inventive subject matteras expressed in the subjoined claims.

1. A computer system for use in processing patient test data from pointof care devices, the computer system comprising: object storage storinga plurality of objects for a plurality of point of care devices, eachobject representing a generic function to be performed on the output ofa point of care device in response to reception of the output of thepoint of care device; instantiation data storage storing instantiationdata for use in instantiating objects as processing objects forfunctions to be performed in response to outputs from point of caredevices, wherein the instantiation data includes data identifying asequence of said objects for at least one said point of care device; anda network interface for the transmission of the instantiation data to atleast one point of care computer storing the objects for the generationof code executable at the point of care computer for a plurality ofprocessing objects to perform a respective plurality of specificprocessing functions to process an output from a point of care device inaccordance with the sequence of objects using the objects stored at thepoint of care computer and the transmitted instantiation data toinstantiate the objects using instantiation data for the point of caredevice.
 2. A computer system according to claim 1, wherein the networkinterface is configured to transmit the objects to the at least onepoint of care computer.
 3. A computer system according to claim 1,wherein the instantiation data includes parameters related to the dataexpected to be output from the at least one point of care device and thedata expected to be received by the at least one point of care device byeach processing object in the course of the output of patient test data.4. A computer system according to claim 1, including a user interfacefor receiving instantiation parameters and object selections from auser.
 5. A computer system according to claim 1, including an interfacefor receiving revisions to the stored objects, wherein the networkinterface is configured to transmit the revised objects to the at leastone point of care computer.
 6. A method for use in processing patienttest data from point of care devices, the method comprising: storing aplurality of objects for a plurality of point of care devices, eachobject representing a generic function to be performed on the output ofa point of care device in response to the output of the point of caredevice; storing instantiation data for use in instantiating objects asprocessing objects for functions to be performed in response to outputsfrom point of care devices, wherein the instantiation data includes dataidentifying a sequence of said objects for at least one said point ofcare device; and transmitting the instantiation data to at least onepoint of care computer storing the objects for the generation of codeexecutable at the point of care computer for a plurality of processingobjects to perform a respective plurality of specific processingfunctions to process an output from a point of care device in accordancewith the sequence of objects using the objects stored at the point ofcare computer and the transmitted instantiation data to instantiate theobjects using instantiation data for the point of care device.
 7. Amethod according to claim 6, including transmitting the objects to theat least one point of care computer.
 8. A method according to claim 6,wherein the instantiation data includes parameters related to the dataexpected to be output from the at least one point of care device and thedata expected to be received by the at least one point of care device byeach processing object in the course of the output of patient test data.9. A method according to claim 6, including receiving instantiationparameters and object selections from a user.
 10. A method according toclaim 6, including receiving revisions to the stored objects, andtransmitting the revised objects to the at least one point of carecomputer.
 11. A non-transitory storage medium storing processorexecutable code, which when executed by at least one processor of acomputer, causes the computer to: store a plurality of objects for aplurality of point of care devices, each object representing a genericfunction to be performed on the output of a point of care device inresponse to the output of the point of care device; store instantiationdata for use in instantiating objects as processing objects forfunctions to be performed in response to outputs from point of caredevices, wherein the instantiation data includes data identifying asequence of said objects for at least one said point of care device; andtransmit the instantiation data to at least one point of care computerstoring the objects for the generation of code executable at the pointof care computer for a plurality of processing objects to perform arespective plurality of specific processing functions to process anoutput from a point of care device in accordance with the sequence ofobjects using the objects stored at the point of care computer and thetransmitted instantiation data to instantiate the objects usinginstantiation data for the point of care device.
 12. A non-transitorystorage medium according to claim 11, wherein the processor executablecode includes code to transmit the objects to the at least one point ofcare computer.
 13. A non-transitory storage medium according to claim11, wherein the instantiation data includes parameters related to thedata expected to be output from the at least one point of care deviceand the data expected to be received by the at least one point of caredevice by each processing object in the course of the output of patienttest data.
 14. A non-transitory storage medium according to claim 11,wherein the processor executable code includes code to generate a userinterface for receiving instantiation parameters and object selectionsfrom a user.
 15. A non-transitory storage medium according to claim 11,wherein the processor executable code includes code to generate aninterface for receiving revisions to the stored objects, wherein thenetwork interface is configured to transmit the revised object to the atleast one point of care computer.
 16. A non-transitory storage mediumstoring data for use in generating code for processing patient test datafrom point of care devices at a point of care computer storing aplurality of objects, each object defining a generic function to beperformed on the output of a point of care device in response to theoutput of the point of care device, the non-transitory storage mediumstoring data comprising: instantiation data for use in instantiatingobjects as processing objects for functions to be performed in responseto outputs from point of care devices, wherein the instantiation dataincludes data identifying a sequence of said objects for at least onesaid point of care device.